Identifying sources of packet drops in a service function chain environment

ABSTRACT

Embodiments are directed to a service function configured to receive, from a service function forwarder, a data packet comprising a bit field to indicate that a packet drop is to be monitored; apply a policy for the data packet; determine that the data packet is to be dropped based on the policy; set a drop-propagate bit in a header of the data packet; and transmit the data packet to the service function forwarder. Embodiments are directed to a service function forwarder configured to receive a data packet from a service function, the data packet comprising a bit set to indicate that a packet drop is to be monitored; generate an Internet Control Message Protocol (ICMP) message, the ICMP message comprising a destination address for the ICMP message identified from the data packet; transmit the ICMP message to the destination address; and drop the data packet from the service function chain.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a Continuation of U.S. application Ser. No. 15/244,369 filed on Aug. 23, 2016, the content of which is incorporated herein by reference in its entirety.

FIELD

This disclosure pertains to identify a cause of a packet drop, and in particular, to detecting and differentiating a packet drop due to policy versus a packet drop due to a malfunctioning service function, in a service function chain environment.

BACKGROUND

In computer networking, network administrators are often concerned with how to best route traffic flows from one end point to another end point across a network. When provisioning a route for a traffic flow, administrators may implement policies to ensure that certain service functions are applied to the packet or the traffic flow as it traverses across the network. Service functions can provide security, wide area network (WAN) acceleration, and loadbalancing. These service functions can be implemented at various points in the network infrastructure, such as the wide area network, data center, campus, etc. Network elements providing these service functions are generally referred to as “service nodes.”

Traditionally, service node deployment is dictated by the network topology. For instance, firewalls are usually deployed at the edge of an administrative zone for filtering traffic leaving or entering the particular zone according to a policy for that zone. With the rise of virtual platforms and more agile networks, service node deployment can no longer be bound by the network topology. To enable service nodes to be deployed anywhere on a network, a solution called Service Function Chaining (SFC) Architecture (IETF draft-ietf-sfc-architecture-04, Sep. 20, 2014) and Network Service Header (NSH) (IETF draft-quinn-sfc-nsh-03, Jul. 3, 2014) have been provided to encapsulated packets or frames to prescribe service paths for traffic flows through the appropriate service nodes. Specifically, Network Service Headers provide data plane encapsulation that utilizes the network overlay topology used to deliver packets to the requisite services.

BRIEF DESCRIPTION OF THE DRAWINGS

To provide a more complete understanding of the present disclosure and features and advantages thereof, reference is made to the following description, taken in conjunction with the accompanying figures, wherein like reference numerals represent like parts.

FIG. 1A illustrates a Service Function Chain (SFC), which may include an initial Classification function, as an entry point into a Service Function Path (SFP), according to some embodiments of the disclosure;

FIGS. 1B-C illustrate different service paths realized using service function chaining, according to some embodiments of the disclosure;

FIG. 2 shows a system view of a Service Chain Function-aware network element for prescribing a service path of a traffic flow, according to some embodiments of the disclosure;

FIG. 3 shows a system view of a service node, according to some embodiments of the disclosure;

FIGS. 4A-B are schematic diagrams of an example service function forwarder handling a data packet in accordance with embodiments of the present disclosure;

FIG. 5 is a schematic diagram of an Internet Control Message Protocol (ICMP) message in accordance with embodiments of the present disclosure;

FIGS. 6A-6B are process flow diagrams for handling a packet by a service function forwarder in accordance with embodiments of the present disclosure; and

FIG. 7 is a schematic diagram illustrating an example header that includes a reserved bit that can be used for a validation bit in accordance with embodiments of the present disclosure.

DETAILED DESCRIPTION

Aspects of the embodiments are directed to a method for packet drop handling in a service function chain environment, the method including receiving a data packet from a service function, the data packet comprising a bit set to indicate that a packet drop is to be monitored; generating an Internet Control Message Protocol (ICMP) message, the ICMP message comprising a destination address for the ICMP message identified from the data packet; transmitting the ICMP message to the destination address; and dropping the data packet from the service function chain.

Aspects of the embodiments are directed to a service function forwarder network element of a service function chain, the service function forwarder including at least one memory element having instructions stored thereon and at least one processors coupled to the at least one memory element and configured to execute the instructions to cause the service function forwarder network element to receive a data packet from a service function, the data packet comprising a bit set to indicate that a packet drop is to be monitored; generate an Internet Control Message Protocol (ICMP) message, the ICMP message comprising a destination address for the ICMP message identified from the data packet; transmit the ICMP message to the destination address; and drop the data packet from the service function chain.

Aspects of the embodiments are directed to a computer-readable non-transitory medium comprising one or more instructions for handling packet drops in a service function chain, the instructions when executed on a processor are operable to receive, from a service function forwarder network element, a data packet comprising a bit field to indicate that a packet drop is to be monitored; apply one or more policies for the data packet; determine that the data packet is to be dropped based on at least one of the one or more policies; set a drop-propagate bit in a header of the data packet; and transmit the data packet to the service function forwarder network element.

Aspects of the embodiments are directed to a computer-readable non-transitory medium comprising one or more instructions for handling packet drops in a service function chain, the instructions when executed on a processor are operable to receive, from a service function forwarder network element, a data packet comprising a bit field to indicate that a packet drop is to be monitored; apply one or more policies for the data packet; determine that the data packet is to be dropped based on at least one of the one or more policies; set a drop-propagate bit in a header of the data packet; and transmit the data packet to the service function forwarder network element.

Aspects of the embodiments are directed to a method performed at a service function of a service function chain, the method including receiving, from a service function forwarder network element, a data packet comprising a bit field to indicate that a packet drop is to be monitored; applying one or more policies for the data packet; determining that the data packet is to be dropped based on at least one of the one or more policies; setting a drop-propagate bit in a header of the data packet; and transmitting the data packet to the service function forwarder network element.

Aspects of the embodiments are directed to a computer-readable non-transitory medium comprising one or more instructions for handling packet drops in a service function chain, the instructions when executed on a processor are operable to receive a data packet from a service function, the data packet comprising a bit set to indicate that a packet drop is to be monitored; generate an Internet Control Message Protocol (ICMP) message, the ICMP message comprising a destination address for the ICMP message identified from the data packet; transmit the ICMP message to the destination address; and drop the data packet from the service function chain.

Some embodiments also include receiving a data packet destined for the service function, the data packet comprising the bit set to indicate that the packet drop is to be monitored; and forwarding the data packet to the service function.

In some embodiments, generating the ICMP message comprises generating the ICMP message with the data packet payload and the destination address from a reply-to field from the data packet header.

In some embodiments, generating the ICMP message comprises generating the ICMP message with an error code identifying one or more policies causing the drop of the packet.

In some embodiments, the instructions further operable when executed to receive a data packet destined for the service function, the data packet comprising the bit set to indicate that the packet drop is to be monitored; and forward the data packet to the service function.

In some embodiments, wherein generating the ICMP message comprises generating the ICMP message with the data packet payload and the destination address from a reply-to field from the data packet header.

In some embodiments, wherein generating the ICMP message comprises generating the ICMP message with an error code identifying one or more policies causing the drop of the packet.

In some embodiments, the instructions are further operable when executed to receive a data packet destined for the service function, the data packet comprising the bit set to indicate that the packet drop is to be monitored; and forward the data packet to the service function.

In some embodiments, generating the ICMP message comprises generating the ICMP message with the data packet payload and the destination address from a reply-to field from the data packet header.

In some embodiments, generating the ICMP message comprises generating the ICMP message with an error code identifying one or more policies causing the drop of the packet.

In some embodiments, the instructions are further operable to apply one or more service functions to the data packet.

In some embodiments, the instructions are further operable to determine whether the bit field that indicates that a packet drop is to be monitored is set, and if the bit field is set, then set the drop-propagate bit in the header of the data packet.

In some embodiments, the instructions are further operable to determine that the bit field that indicates that a packet drop is to be monitored is not set, and drop the packet.

Some embodiments also include applying one or more service functions to the data packet.

Some embodiments also include determining whether the bit field that indicates that a packet drop is to be monitored is set, and if the bit field is set, then setting the drop-propagate bit in the header of the data packet.

Some embodiments also include determining that the bit field that indicates that a packet drop is to be monitored is not set, and dropping the packet.

In a service function chain (SFC) environment, a packet can flow over a set of Service Functions (SFs) for packet treatment. A packet flowing over a specific service function path (SFP) might be dropped due to different reasons, such as:

Service Functions like Firewall drop a packet due 1. to firewall policy;

2. Service Functions like DPI, Anomaly detection, etc., might drop a packet on detecting certain signature etc.;

3. Malfunctioning Service Function (abruptly dropping it).

This disclosure describes detecting and differentiating whether a packet drop is due to policy (expected) or a malfunctioning SF (unexpected).

This disclosure describes leveraging a header bit added into the data plane traffic packet that can be used between a service function forwarder (SFF) and an SF so that an Operator can differentiate such failures. The use of an indicator bit can facilitate troubleshooting activities within the service function path.

This disclosure describes an source (such as an operator or other cloud-computing operator) selecting to know about whether to receive specific drop errors and causes. An operator can elect to check if data traffic is dropped due to policy or unexpected behavior, and can set a Validation bit (V), an O bit, or another bit in header, that serves as a flag to an SF to provide information on a policy-based drop. The validation bit, O bit, or other bit, can be set by a classifier network element or a mid-stream SFF. In embodiments, the V-bit can be one of the reserved bits from the packet header. The SF that is instructed by local policy to drop the packet will set a new bit (DP or Drop Propagate bit) in the header and forward back to SFF. SFF will drop the packet and will generate error message stating “Drop due to policy.” In case of unexpected or malfunctioning drop, the initiator (OAM server or Classifier) will not receive any such error message that differentiates such two types of drops.

Basics of Network Service Chaining or Service Function Chains in a Network

To accommodate agile networking and flexible provisioning of network nodes in the network, Service Function Chains (SFC) can be used to ensure an ordered set of Service Functions (SF) to be applied to packets and/or frames of a traffic flow. SFCs provides a method for deploying SFs in a way that enables dynamic ordering and topological independence of those SFs. A service function chain can define an ordered set of service functions that is applied to packets and/or frames of a traffic flow, where the ordered set of service functions are selected as a result of classification. The implied order may not be a linear progression as the architecture allows for nodes that copy to more than one branch. The term service chain is often used as shorthand for service function chain.

FIG. 1A illustrates a Service Function Chain (SFC), which may include an initial service classification function 102, as an entry point into a Service Function Path (SFP) 104 (or service path). The (initial) service classification function 102 prescribes a service path, and encapsulates a packet or frame with the service path information which identifies the service path. The classification potentially adds metadata, or shared context, to the SFC encapsulation part of the packet or frame. The service function path 104 may include a plurality of service functions (shown as “SF1”, . . . , “SFN”).

A service function can be responsible for specific treatment of received packets. A service function can act at the network layer or other OSI layers (e.g., application layer, presentation layer, session layer, transport layer, data link layer, and physical link layer). A service function can be a virtual instance or be embedded in a physical network element such as a service node. When a service function or other modules of a service node is executed by the at least one processors of the service node, the service function or other modules can be configured to implement any one of the methods described herein. Multiple service functions can be embedded in the same network element. Multiple instances of the service function can be enabled in the same administrative SFC-enabled domain. A non-exhaustive list of SFs includes: firewalls, WAN and application acceleration, Deep Packet Inspection (DPI), server load balancers, NAT44, NAT64, HOST_ID injection, HTTP Header Enrichment functions, TCP optimizer, etc. An SF may be SFC encapsulation aware, that is it receives, and acts on information in the SFC encapsulation, or unaware in which case data forwarded to the service does not contain the SFC encapsulation.

A Service Node (SN) can be a physical network element (or a virtual element embedded on a physical network element) that hosts one or more service functions (SFs) and has one or more network locators associated with it for reachability and service delivery. In many standardization documents, “service functions” can refer to the service nodes described herein as having one or more service functions hosted thereon. Service Function Path (SFP) (or sometimes referred simply as service path) relates to the instantiation of a SFC in the network. Packets follow a service path from a classifier through the requisite service functions.

FIGS. 1B-C illustrate different service paths realized using service function chaining. These service paths can be implemented by encapsulating packets of a traffic flow with a network service header (NSH) or some other suitable packet header which specifies a desired service path (e.g., by identifying a particular service path using service path information in the NSH). In the example shown in FIG. 1B, a service path 120 can be provided between end point 160 and endpoint 180 through service node 106 and service node 110. In the example shown in FIG. 1C, a service path 130 (a different instantiation) can be provided between end point 170 and endpoint 190 through service node 106, service node 108, and service node 112.

Network Service Header (NSH) Encapsulation

Generally speaking, an NSH includes service path information, and NSH is added to a packet or frame. For instance, an NSH can include a data plane header added to packets or frames. Effectively, the NSH creates a service plane. The NSH includes information for service chaining, and in some cases, the NSH can include metadata added and/or consumed by service nodes or service functions. The packets and NSH are encapsulated in an outer header for transport. To implement a service path, a network element such as a service classifier (SCL) or some other suitable SFC-aware network element can process packets or frames of a traffic flow and performs NSH encapsulation according to a desired policy for the traffic flow.

FIG. 2 shows a system view of SFC-aware network element, e.g., such as a (initial) service classifier (SCL), for prescribing a service path of a traffic flow, according to some embodiments of the disclosure. Network element 202 includes processor 204, (computer-readable non-transitory) memory 206 for storing data and instructions. Furthermore, network element 202 includes service classification function 208 and service header encapsulator 210 (both can be provided by processor 204 when processor 204 executes the instructions stored in memory 206).

The service classification function 208 can process a packet of a traffic flow and determine whether the packet requires servicing and correspondingly which service path to follow to apply the appropriate service. The determination can be performed based on business policies and/or rules stored in memory 206. Once the determination of the service path is made, service header encapsulator 210 generates an appropriate NSH having identification information for the service path and adds the NSH to the packet. The service header encapsulator 210 provides an outer encapsulation to forward the packet to the start of the service path. Other SFC-aware network elements are thus able to process the NSH while other non-SFC-aware network elements would simply forward the encapsulated packets as is. Besides inserting an NSH, network element 202 can also remove the NSH if the service classification function 208 determines the packet does not require servicing.

Network Service Headers

A network service header (NSH) can include a (e.g., 64-bit) base header, and one or more context headers. Generally speaking, the base header provides information about the service header and service path identification (e.g., a service path identifier), and context headers can carry opaque metadata (such as the metadata described herein reflecting the result of classification). For instance, an NSH can include a 4-byte base header, a 4-byte service path header, and optional context headers. The base header can provide information about the service header and the payload protocol. The service path header can provide path identification and location within a path. The (variable length) context headers can carry opaque metadata and variable length encoded information. The one or more optional context headers make up a context header section in the NSH. For instance, the context header section can include one or more context header fields having pieces of information therein, describing the packet/frame. Based on the information in the base header, a service function of a service node can derive policy selection from the NSH. Context headers shared in the NSH can provide a range of service-relevant information such as traffic classification. Service functions can use NSH to select local service policy.

Service Nodes and Proxy Nodes

Once properly encapsulated, the packet having the NSF is then forwarded to one or more service nodes where service(s) can be applied to the packet/frame. FIG. 3 shows a system view of a service node, according to some embodiments of the disclosure. Service node 300, generally a network element, can include processor 302, (computer-readable non-transitory) memory 304 for storing data and instructions. Furthermore, service node 300 includes service function(s) 306 (e.g., for applying service(s) to the packet/frame, classifying the packet/frame) and service header processor 308. The service functions(s) 306 and service header processor 306 can be provided by processor 302 when processor 302 executes the instructions stored in memory 304. Service header processor 308 can extract the NSH, and in some cases, update the NSH as needed. For instance, the service header processor 308 can decrement the service index if a service index=0 is used to indicate that a packet is to be dropped by the service node 300. In another instance, the service header processor 308 or some other suitable module provide by the service node can update context header fields if new/updated context is available.

Example Implementations

This disclosure describes a Service Function (such as a Firewall, DPI, etc.) that when the SF is expected to drop a packet due to policy and if a new bit is set by the classifier (e.g., a Data Validation bit or an O bit), the SF will set a new bit (e.g., Drop-Propagate bit) set in the header of the packet, and forward the packet to the SFF.

The SFF can generate an Internet Control Message Protocol (ICMP) message and forward to the relevant node (Classifier/Initiator/Server, etc.) using a new ICMP code and include the header from the to-be-dropped packet.

The classifier will be instructed to include Validation bit (or the O bit) in traffic flows that needs drop monitoring and differentiate if the missing packets are due to policy or unexpected drop. The classifier in addition will include a “reply-to” address in Metadata. This address is used to send the ICMP reply back from the SFF.

FIGS. 4A-B are schematic diagrams of an example service function forwarder handling a data packet in accordance with embodiments of the present disclosure. FIG. 4A is a schematic diagram 400 of a service function forwarder (SFF) 402 that receives a data packet 406 that includes a bit set in the data packet header indicating a request to report data packet drop due to policy. For example, the data packet header can have an O bit set or a data validation bit set that indicates to a service function (SF) 404 to report a packet drop due to policy reasons to the SFF 402.

Upon receiving the packet 406, the SFF 402 can process the packet 406 based on the intended SF 404 from the SFP and SI information from the packet header. The SF 404 can process the packet in accordance to the SF's function. In some embodiments, the SF 404 can determine that policy enforcement indicates that the SF 404 should drop the packet. The SF 404 can set another bit in the packet header that indicates to the SFF 402 that the SFF 402 should generate an Internet Control Message Protcol (ICMP) message. This bit can be a drop propagate (DP) bit in the packet header. The SF 404 can then forward the packet back to the SFF 402.

In embodiments where a data validation bit or O bit (or other bit) is not set, then the SF 404 can drop the packet and forgo setting the DP bit and forgo forwarding the packet to the SFF 402.

In FIG. 4B, the SFF 402 can receive a packet from the SF 404 that includes a DP bit set. The SFF 402, upon receiving a packet with DP flag, will drop the packet and generate an Internet Control Message Protocol (ICMP) message with a new code and include the dropped packet header and forward the ICMP message to the “reply-to” address identified from the packet header.

The concepts described herein are applicable for probe packets and data packets and is scalable as it is not required to be done on all flows/packets.

FIG. 5 is a schematic diagram of an Internet Control Message Protocol (ICMP) message 500 in accordance with embodiments of the present disclosure. The ICMP message 500 can include an IP header 502 that identifies the reply-to address and the source IP from the service function forwarder. The ICMP message 500 can also include as much as the initial packet payload 504 as is possible within the payload of the ICMP message 500.

FIGS. 6A-6B are process flow diagrams for handling a packet by a service function forwarder in accordance with embodiments of the present disclosure. FIG. 6A is a process flow diagram 600 for processing a data packet. At the outset, an operator can use a classifier or a service function forwarder to set a data validation bit or an O bit or another bit flag in a data packet header (602). The data packet can be sent through a service function chain based on the service path identifier and service index identified in the data packet header (604).

A service function forwarder (SFF) can receive the data packet and forward the packet to a service function (606). The service function (SF) can process the data packet based on the information from the data packet header; the SF can also apply one or more policies for the data packet based on the information from the data packet header (608). In embodiments, the policy or policies implemented can indicate that the data packet should be dropped (610).

The SF can determine from the data packet header whether the validation bit or the O bit (or other bit flag is set that indicates the operator's election to monitor causes of dropped packets, but for ease, this bit is referred to here as a validation bit) (612). If the SF determines that the validation bit is not set, then the SF can drop the data packet and take no further action for that data packet (618).

If the SF determines that the validation bit is set, then the SF can set a drop-propagate (DP) bit in the data packet header (614). The SF can then send the data packet with the DP bit set to the SFF (616).

FIG. 6B is a process flow diagram 650 for handling a data packet that includes a drop-propagate (DP) bit set. The service function forwarder (SFF) can receive a data packet from the service function (SF), the data packet including a DP bit set (652). The SFF can identify from the data packet header that the DP bit has been set (654) The SFF can generate an Internet Control Message Protocol (ICMP) message with the reply-to information from the data packet header (656). The ICMP message can also include new coding, data packet payload, header information, etc. The SFF can send the ICMP to the destination identified in the reply-to address (658). The SFF can drop the data packet (660).

In some embodiments, the last SFF in a service function chain can decapsulate the data packet's NSH header, and can send a positive notification message (ICMP with a new code) when the Validation bit is set, that confirms that the packet has successfully flowed through the service function chain. When an operator sets the validation bit in a data traffic, the operator can receive the following:

1. If allowed by policies will receive a positive response from last SFF.

2. If dropped by policies, will receive an error code from connected SFF.

3. If dropped abruptly, will not receive any response.

If the packet drops, but the source that requested the monitoring does not receive the ICMP message, then the source can determine that the packet drop was in error (e.g., due to a malfunctioning SF or other issue with the service function chain, or with the packet itself). If the source does receive the ICMP message, then the source can determine the cause of the packet drop, such as which policy was enforced and where in the service function chain the policy was enforced.

FIG. 7 is a schematic diagram illustrating an example packet header 700 that includes a reserved bit that can be used for a validation bit in accordance with embodiments of the present disclosure. The packet header 700 includes one or more reserve bits 702. One of the reserved bits 702 can be used as a validation bit (V). When V=1, the SF is signaled to track the source of a packet drop, as described above. Also shown in FIG. 7 is the O bit 704. In embodiments, the O bit 704 can be used to signal the SF to monitor packet drop sources, though is used for other operations, as well.

Variations and Implementations

Within the context of the disclosure, a network used herein represents a series of points, nodes, or network elements of interconnected communication paths for receiving and transmitting packets of information that propagate through a communication system. A network offers communicative interface between sources and/or hosts, and may be any local area network (LAN), wireless local area network (WLAN), metropolitan area network (MAN), Intranet, Extranet, Internet, WAN, virtual private network (VPN), or any other appropriate architecture or system that facilitates communications in a network environment depending on the network topology. A network can comprise any number of hardware or software elements coupled to (and in communication with) each other through a communications medium.

In one particular instance, the architecture of the present disclosure can be associated with a service provider deployment. In other examples, the architecture of the present disclosure would be equally applicable to other communication environments, such as an enterprise wide area network (WAN) deployment, The architecture of the present disclosure may include a configuration capable of transmission control protocol/internet protocol (TCP/IP) communications for the transmission and/or reception of packets in a network.

As used herein in this Specification, the term ‘network element’ is meant to encompass any of the aforementioned elements, as well as servers (physical or virtually implemented on physical hardware), machines (physical or virtually implemented on physical hardware), end user devices, routers, switches, cable boxes, gateways, bridges, loadbalancers, firewalls, inline service nodes, proxies, processors, modules, or any other suitable device, component, element, proprietary appliance, or object operable to exchange, receive, and transmit information in a network environment. These network elements may include any suitable hardware, software, components, modules, interfaces, or objects that facilitate the network service header features/operations thereof. This may be inclusive of appropriate algorithms and communication protocols that allow for the effective exchange of data or information.

In one implementation, nodes with NSH capabilities may include software to achieve (or to foster) the functions discussed herein for providing the NSH-related features/functions where the software is executed on one or more processors to carry out the functions. This could include the implementation of instances of service functions, service header processors, metadata augmentation modules and/or any other suitable element that would foster the activities discussed herein. Additionally, each of these elements can have an internal structure (e.g., a processor, a memory element, etc.) to facilitate some of the operations described herein. In other embodiments, these functions may be executed externally to these elements, or included in some other network element to achieve the intended functionality. Alternatively, these nodes may include software (or reciprocating software) that can coordinate with other network elements in order to achieve the functions described herein. In still other embodiments, one or several devices may include any suitable algorithms, hardware, software, components, modules, interfaces, or objects that facilitate the operations thereof.

In certain example implementations, the NSH-related functions outlined herein may be implemented by logic encoded in one or more non-transitory, tangible media (e.g., embedded logic provided in an application specific integrated circuit [ASIC], digital signal processor [DSP] instructions, software [potentially inclusive of object code and source code] to be executed by one or more processors, or other similar machine, etc.). In some of these instances, one or more memory elements can store data used for the operations described herein. This includes the memory element being able to store instructions (e.g., software, code, etc.) that are executed to carry out the activities described in this Specification. The memory element is further configured to store databases or metadata disclosed herein. The processor can execute any type of instructions associated with the data to achieve the operations detailed herein in this Specification. In one example, the processor could transform an element or an article (e.g., data) from one state or thing to another state or thing. In another example, the activities outlined herein may be implemented with fixed logic or programmable logic (e.g., software/computer instructions executed by the processor) and the elements identified herein could be some type of a programmable processor, programmable digital logic (e.g., a field programmable gate array [FPGA], an erasable programmable read only memory (EPROM), an electrically erasable programmable ROM (EEPROM)) or an ASIC that includes digital logic, software, code, electronic instructions, or any suitable combination thereof.

Any of these elements (e.g., the network elements, service nodes, etc.) can include memory elements for storing information to be used in achieving the NSH-related features, as outlined herein. Additionally, each of these devices may include a processor that can execute software or an algorithm to perform the NSH-related features as discussed in this Specification. These devices may further keep information in any suitable memory element [random access memory (RAM), ROM, EPROM, EEPROM, ASIC, etc.], software, hardware, or in any other suitable component, device, element, or object where appropriate and based on particular needs. Any of the memory items discussed herein should be construed as being encompassed within the broad term ‘memory element.’ Similarly, any of the potential processing elements, modules, and machines described in this Specification should be construed as being encompassed within the broad term ‘processor.’ Each of the network elements can also include suitable interfaces for receiving, transmitting, and/or otherwise communicating data or information in a network environment.

Additionally, it should be noted that with the examples provided above, interaction may be described in terms of two, three, or four network elements. However, this has been done for purposes of clarity and example only. In certain cases, it may be easier to describe one or more of the functionalities of a given set of flows by only referencing a limited number of network elements. It should be appreciated that the systems described herein are readily scalable and, further, can accommodate a large number of components, as well as more complicated/sophisticated arrangements and configurations. Accordingly, the examples provided should not limit the scope or inhibit the broad techniques of using and augmenting NSH metadata, as potentially applied to a myriad of other architectures.

It is also important to note that the various steps described herein illustrate only some of the possible scenarios that may be executed by, or within, the nodes with NSH capabilities described herein. Some of these steps may be deleted or removed where appropriate, or these steps may be modified or changed considerably without departing from the scope of the present disclosure. In addition, a number of these operations have been described as being executed concurrently with, or in parallel to, one or more additional operations. However, the timing of these operations may be altered considerably. The preceding operational flows have been offered for purposes of example and discussion. Substantial flexibility is provided by nodes with NSH capabilities in that any suitable arrangements, chronologies, configurations, and timing mechanisms may be provided without departing from the teachings of the present disclosure.

It should also be noted that many of the previous discussions may imply a single client-server relationship. In reality, there is a multitude of servers in the delivery tier in certain implementations of the present disclosure. Moreover, the present disclosure can readily be extended to apply to intervening servers further upstream in the architecture, though this is not necessarily correlated to the ‘m’ clients that are passing through the ‘n’ servers. Any such permutations, scaling, and configurations are clearly within the broad scope of the present disclosure.

Numerous other changes, substitutions, variations, alterations, and modifications may be ascertained to one skilled in the art and it is intended that the present disclosure encompass all such changes, substitutions, variations, alterations, and modifications as falling within the scope of the appended claims. In order to assist the United States Patent and Trademark Office (USPTO) and, additionally, any readers of any patent issued on this application in interpreting the claims appended hereto, Applicant wishes to note that the Applicant: (a) does not intend any of the appended claims to invoke paragraph six (6) of 35 U.S.C. section 112 as it exists on the date of the filing hereof unless the words “means for” or “step for” are specifically used in the particular claims; and (b) does not intend, by any statement in the specification, to limit this disclosure in any way that is not otherwise reflected in the appended claims. 

What is claimed is:
 1. A method for packet drop handling in a service function chain environment, the method comprising receiving a data packet from a service function in response to the data packet comprising a first bit set to indicate that a packet is to be monitored and a second bit set to indicate that a packet is to be dropped; generating, in response to the receiving, a second message comprising a destination address for a first message identified from the data packet; transmitting the second message to the destination address; and dropping the data packet from the service function chain; wherein the second message represents a communication to the destination address that the drop of the data packet was intentional.
 2. The method of claim 1, further comprising: receiving a data packet destined for the service function, the data packet comprising the first and second bits; and forwarding the data packet to the service function.
 3. The method of claim 1, wherein generating the second message comprises generating the second message with a data packet payload and the destination address from a reply-to field from a data packet header.
 4. The method of claim 1, wherein generating the second message comprises generating the second message with an error code identifying one or more policies causing the drop of the packet.
 5. The method of claim 1, wherein the data packet comprises one or more reserved bits in a packet header, and the bit set is one of the reserved bits from the packet header.
 6. The method of claim 5, wherein the reserved bit in the data packet comprises a validation bit.
 7. The method of claim 1, wherein the data packet comprises a packet header comprising an O bit, wherein the bit set is the O bit.
 8. A computer-readable non-transitory medium comprising one or more instructions for handling packet drops in a service function chain, the instructions when executed on a processor are operable to perform operations comprising: receiving a data packet from a service function in response to the data packet comprising a first bit set to indicate that a packet is to be monitored and a second bit set to indicate that a packet is to be dropped; generating, in response to the receiving, a second message comprising a destination address for a first message identified from the data packet; transmitting the second message to the destination address; and dropping the data packet from the service function chain; wherein the second message represents a communication to the destination address that the drop of the data packet was intentional.
 9. The computer-readable non-transitory medium of claim 8, the instructions further operable when executed to receive a data packet destined for the service function, the data packet comprising the first and second bits, and forward the data packet to the service function.
 10. The computer-readable non-transitory medium of claim 8, wherein generating the second message comprises generating the second message with a data packet payload and the destination address from a reply-to field from a data packet header.
 11. The computer-readable non-transitory medium of claim 8, wherein generating the second message comprises generating the second message with an error code identifying one or more policies causing the drop of the packet.
 12. The computer-readable non-transitory medium of claim 8, wherein the data packet comprises one or more reserved bits in a packet header, and the bit set is one of the reserved bits from the packet header.
 13. The computer-readable non-transitory medium of claim 12, wherein the reserved bit in the data packet comprises a validation bit.
 14. The computer-readable non-transitory medium of claim 8, wherein the data packet comprises a packet header comprising an O bit, wherein the bit set is the O bit.
 15. A service function forwarder network element of a service function chain, the service function forwarder comprising: at least one memory element having instructions stored thereon; at least one processors coupled to the at least one memory element and configured to execute the instructions to cause the service function forwarder network element to perform operations comprising: receiving a data packet from a service function in response to the data packet comprising a first bit set to indicate that a packet is to be monitored and a second bit set to indicate that a packet is to be dropped; generating, in response to the receiving, a second message comprising a destination address for a first message identified from the data packet; transmitting the second message to the destination address; and dropping the data packet from the service function chain; wherein the second message represents a communication to the destination address that the drop of the data packet was intentional.
 16. The service function forwarder network element of claim 15, the instructions further operable when executed to receive a data packet destined for the service function, the data packet comprising the first and second bits set.
 17. The service function forwarder network element of claim 15, wherein generating the second message comprises generating the second message with an error code identifying one or more policies causing the drop of the packet.
 18. The service function forwarder network element of claim 15, wherein generating the second message comprises generating the second message with a data packet payload and the destination address from a reply-to field from a data packet header.
 19. The service function forwarder network element of claim 15, wherein the data packet comprises one or more reserved bits in a packet header, and the bit set is one of the reserved bits from the packet header.
 20. The service function forwarder network element of claim 19, wherein the reserved bit in the data packet comprises a validation bit. 